Electric vehicle charging network services

ABSTRACT

To provide remote services, including dynamic, interactive assistance to electric vehicle (EV) users, a central server is arranged for electronic communications with EVs ( 15 ) and with client devices ( 11 ). The server also communicates with at least one EV charging station network, which in turn communicate with individual charging stations ( 30 ). Remote services may include trip planning, locating charging stations, checking availability and suitability of charging stations, making reservations at charging stations, and updating plans en route. The server collects data from the EV and analyzes the data to determine various statistics. The system advises a user on readiness of the EV to complete a proposed trip before recharging the EV batteries. Client devices may include smart phones, computers, or a head unit in the EV. Application software programs are executable on the client devices to provide user interfaces for accessing the remote services and for communicating with the central server.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/275,210, filed on Sep. 23, 2016, which is a divisional of U.S. patentapplication Ser. No. 14/594,923, filed on Jan. 12, 2015, now issued asU.S. Pat. No. 9,476,725, which is a divisional of U.S. patentapplication Ser. No. 13/736,805, filed on Jan. 8, 2013, now issued asU.S. Pat. No. 8,965,669, which claims the benefit of U.S. provisionalpatent application Ser. No. 61/584,688 filed Jan. 9, 2012, and all areincorporated herein by this reference.

COPYRIGHT NOTICE

© 2012-2013 Airbiquity Inc. A portion of the disclosure of this patentdocument contains material which is subject to copyright protection. Thecopyright owner has no objection to the facsimile reproduction by anyoneof the patent document or the patent disclosure, as it appears in thePatent and Trademark Office patent file or records, but otherwisereserves all copyright rights whatsoever. 37 CFR § 1.71(d).

TECHNICAL FIELD

This invention pertains to methods and apparatus for networked electricvehicle (EV) user support services.

BACKGROUND OF THE INVENTION

Conventional technical schemes are available for assisting a driver indetermining an appropriate time to “fill up” their vehicle. Theconventional technical schemes typically involve a fuel gauge installedin the dashboard of a vehicle. The fuel gauge may have a full marking,an empty marking, other markings in between, and a needle indicatingcurrent fuel level relative to the markings. The gauge may also includea fuel light to activate when current fuel level reaches a presetfraction of maximum fuel. A driver can use the fuel gauge to determinean appropriate time to “fill up”.

While these conventional technical schemes for assisting a driver indetermining an appropriate time to “fill up” or refuel their vehicle,partially or completely, are typically sufficient for gasoline poweredvehicles, electric vehicle usage is different than gasoline poweredvehicle usage. In particular, electric vehicles considered as a wholetypically have a shorter range (distance between “fill-ups”) thangasoline powered vehicles. Electric vehicles typically require severalhours to recharge, which is longer than the minutes needed to refuel agasoline powered vehicle. Also, electric charging stations are notcurrently ubiquitous (as compared to gasoline stations). In view of theforgoing, a technical solution is needed to assist a driver of anelectric vehicle in determining an appropriate time and place torecharge their vehicle battery.

SUMMARY OF THE INVENTION

The following is a summary of the invention in order to provide a basicunderstanding of some aspects of the invention. This summary is notintended to identify key/critical elements of the invention or todelineate the scope of the invention. Its sole purpose is to presentsome concepts of the invention in a simplified form as a prelude to themore detailed description that is presented later.

In one aspect, this disclosure describes a feature for EV users toreduce anxiety that may be caused by uncertainty as to whether or not anelectric vehicle has sufficient charge to carry out its agenda for theremainder of the day. In other aspects, software analyzes a plannedroute, in view of a variety of information including but not limited toa history of prior usage data for the vehicle, driving style, plannedroute, current traffic conditions, and current charge or energy level ofthe vehicle batteries, to determine whether it will have sufficientrange to complete the proposed trip.

In another aspect, the system provides information to a user regardingcharging stations located either nearby or along a proposed route, forrecharging the vehicle. Range analysis, mentioned above, combined withroute planning and charging station data can be used to identifycharging stations along the route, to check their suitability for thevehicle, to check their availability, and to make a reservation forcharging at a selected charging station.

In a preferred embodiment, some user services and features are providedthrough communications between a “client” device in the car and acentral server computer, further explained below. Preferably, thecentral server is arranged for communication with at least one chargingstation network.

Additional aspects and advantages of this invention will be apparentfrom the following detailed description of preferred embodiments, whichproceeds with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified diagram illustrating a system to deliver driverservices to operators of electric vehicles (EV).

FIG. 2 is an example of a screen display for login to a clientapplication consistent with the present disclosure.

FIG. 3 is an example of a client application screen display indicating areadiness status of the electric vehicle.

FIG. 4 is an example of a client application screen display showingicons corresponding to a variety of available user services andfeatures.

FIG. 5 is an example of a client application screen display showingexamples of remote control features.

FIG. 6 is an example of a client application screen display regardingspecification of drive times.

FIG. 7 shows an example of a listing of drive times by day of the week.

FIG. 8 is an example of a client application screen display for addingor “programming” a drive time.

FIG. 9 is a continuation of the screen display of FIG. 8, which may beaccessed by scrolling.

FIG. 10 is an example of a client application screen display regardingeco-charge profiles, to take advantage of variation in electricityprices for charging an electric vehicle.

FIG. 11 is an example of a client application screen display showing alisting of eco-charge profiles per location.

FIG. 12 is an example of a client application screen display forselecting a charging location to define a charge profile.

FIG. 13 shows an example of a client application screen displaycomprising a map showing the user's current location and a currentlocation of the electric vehicle.

FIG. 14 is an example of a client application screen display showing asuggested route on a map for walking from the user's current location tothe current location of the electric vehicle.

FIG. 15 is an example of a client application screen display showing thesuggested route of FIG. 14 in a list view.

FIG. 16 is an example of a client application screen display for atravel planner feature.

FIG. 17 shows an example of a client application screen display foradding a route point or adding a charging station for planning a trip.

FIG. 18 is an example of a client application screen display forentering a place or address as part of planning a trip.

FIG. 19 shows a listing of locations that were found based on the dataentered in FIG. 18.

FIG. 20 is a an example of a map display showing the locations that arelisted in the screen display of FIG. 19, enabling user selection of adesired location or route point by touching the screen at thecorresponding location indicator.

FIG. 21 is an example of a client application screen display showing theEV current location and status, along with the selected route point.

FIG. 22 is an example of a client application screen display forconducting a search for charging stations near a current location of theEV.

FIG. 23 is a continuation of the screen display of FIG. 22 which may beaccessed, for example, by scrolling.

FIG. 24 is an example of a client application screen display showing alisting of charging stations found near a requested or current location.

FIG. 25 is a map display showing locations of the charging stations thatare listed in the display of FIG. 24.

FIG. 26 is an example of a client application screen display showingdetails of a selected charging station, including its present status.

FIG. 27 is an example of a client application screen display showing theelectric vehicle's current location and status, and showing route pointsthat have been selected for a trip.

FIG. 28 is an example of a client application screen display arrangedfor user to enter a home address, which may be used as an anchor pointor route point.

FIG. 29 is an example of a client application screen display showing acar's present location and status, and a series of route points for atrip.

FIG. 30 is an example of a client application screen display regardingplanning a proposed trip.

FIG. 31 is a continuation from FIG. 30 showing details of the proposedroute.

FIG. 32 is an example of a map screen display illustrating the proposedroute.

FIG. 33 is an example of a client application screen display forsearching for a charging station near a defined location.

FIG. 34 is a continuation of the display of FIG. 33 showing more detailsfor a charging station search.

FIG. 35 is an example of a screen display showing a listing of chargingstations that were found pursuant to the search defined in FIGS. 33-34.

FIG. 36 is an example of a map display showing the locations of thecharging stations listed in the screen display of FIG. 35.

FIG. 37 is an example of a screen display showing details of a selectedcharging station with an option to reserve charging time at the chargingstation.

FIG. 38 is an example of a client application screen display showing anupcoming commute and a series of stored commutes, along with travel timeinformation based on current and statistically projected trafficconditions.

FIG. 39 is an example of a client application screen display showing ahealth report for the electric vehicle.

FIG. 40 is an example of a client application screen display showinginformation about a user's driving style based on a history of trips,and displaying information reflecting monetary savings and energyconsumption.

FIG. 41 is an example of screen display showing aggregated informationfor a given group or fleet of electric vehicles.

FIG. 42 is an example of a client application screen display formanaging a user's account and other operations.

FIG. 43 may be a continuation of FIG. 42 for maintaining a user profile.

FIG. 44 is a continuation of FIG. 43 for maintaining a user profile.

FIG. 45 is an example of a screen display regarding a user profileshowing additional options.

FIG. 46 is an example of a screen display for updating a user passwordfor a mobile application account.

FIG. 47 is an example of a client application screen display for makinga reservation at a selected charging station.

FIG. 48 is a continuation of the prior screen display for setting moredetails of a charging station reservation.

FIG. 49 is an example of a screen display confirming a charging stationreservation.

FIG. 50 is an example of a screen display related to canceling areservation at an EV charging station.

FIG. 51 is an example of a client application screen display regarding astored commute to work, with information on travel time and an alternateroute.

FIG. 52 is an example of a map display illustrating a proposed route.

FIG. 53 is an example of a screen display of the map of FIG. 52 showingan indication of traffic conditions.

FIG. 54 is an example of a web page interface to a server for electricvehicle services.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIG. 1 illustrates a system to assist a driver of an electric vehicle(15). For example, the system can be used for determining an appropriatetime or place to recharge the vehicle battery. The system 100 includes aserver 12, which may comprise one or more servers and other resources,wherever located. It has suitable means for communications over one ormore networks, such as the Internet and/or a telecommunications network.It may communicate via a suitable gateway to a wirelesstelecommunications network. In some embodiments, the wirelesstelecommunications network may be used for server communications with aclient device 11. In some cases, in-band signaling may be used for datacommunications during a voice channel call on the wirelesstelecommunications network. In some embodiments, a broadband or WiFinetwork may be used for server communications with a client device 11.Any or all of the above, as well as a wired network, POTS, cable, orother means not yet known may be used for server communications withother one or more EV charging station networks (not shown), which inturn may communicate with individual charging stations 30.

A client device 11 may comprise, in some embodiments, a personalportable device (cell phone, PDA, laptop, tablet computer, etc.), avehicle “head unit,” a desktop computer, or the like. The servers 12typically include a memory device to store instructions that, ifexecuted by a computing device, perform operations that will bedescribed herein as operations of the server 12.

The server 12 may collect, from an electric vehicle or a computingdevice coupled to the electric vehicle, data for learning drivingpatterns. In a preferred embodiment, the server transmits a query orrequest to a wireless communication device embedded in the EV to acquirehistorical driving data. In an alternative embodiment, a client device11 in or near the EV may be used to acquire the data and transmit it tothe server. The server 12 generates a driving history based on thecollected data. The server 12 may store the driving history in adatabase. The database may be organized, for example, as a plurality ofentries or records, each indicating a particular driving trip of thesubject vehicle. Data may be aggregated over a fleet of vehicles.

A trip record may include, for example, a distance traveled by theelectric vehicle, how much energy was used by the electric vehicleduring the trip, and a time stamp indicating a date and time that thetrip started and/or ended. Additional information in a trip record mayinclude a route, start and stop locations, way points, traffic data andor topological data. It may include weather conditions or temperature,traffic conditions and other variables. A detailed record may includeperiodic speed readings.

The server 12 analyzes the database entries. In one example, the server12 may identify patterns based on the database entries, i.e. adifference between certain days of the week vs. other days of the weeks,which has some consistency across weeks, i.e. observing that 18 kilowatthours are typically used on Wednesday while 15 kilowatt hours aretypically used on a Thursday.

In one example, if a pattern is identified, the analysis may include theserver 12 interfacing with a calendaring application to determine futuretrips that would skew an expected usage based on an identified pattern.The server 12 may check the appointment for address information.However, if the appointment lists a person but not address information,the server 12 may obtain address information listed for the person fromthe appointment using contacts or some other database.

In one example, the server 12 may determine an expected energy usage fora time period to occur based on the analysis. The determination canconsider parameters such as temperature, weather conditions,characteristics of expected travel when they vary from historical travel(such as the use of a hilly route or a high speed freeway that are notnormally used), traffic, tire pressure, vehicle load (number ofpassengers), or other variables. In one example, the determination mayinclude comparing a current or expected temperature for the time periodwith an average temperature based on prior corresponding time periods.Energy usage may be higher than expected from the identified pattern ifthe day is unusually cold, for example, because a driver may be expectedto utilize the vehicle's heater more than usual. Conversely, in hotweather the air conditioning will have a similar impact. HVAC in generalrequires energy from the batteries. Also, weather forecasts or currentconditions can also be used in the determination. For example, expectedenergy usage may be different than expected based on an identifiedpattern if there is currently snow on the ground or other weatherconditions that could affect frictional coefficients of the tires of theelectric vehicle.

The server 12 may generate a presentation for a driver of the electricvehicle based on the determination. The generated presentation is to bedisplayed using the client 11 (in one example the generated presentationmay be displayed on a visual and/or audio display of a vehicle head unitof the electric vehicle).

The generated presentation may indicate whether the amount of energycurrently stored in the battery of the electric vehicle is greater thanthe expected energy usage for a particular time period, e.g. the rest ofthe day, based on the determination. In one example, the generatedpresentation specifies that the driver is “Ready To Go”™ (“Ready to Go”is a trademark of Airbiquity Inc.) if the amount of energy currentlystored in the battery of the electric vehicle is greater than theexpected energy usage for the rest of the day. In an embodiment thedetermination may be made not for the whole day, but for the morningcommute to work, for example, or return home from the office. A screenfor the example described in the immediately preceding paragraph isshown in FIG. 3. The shading extending from 0 to below 50% representsthe determination of energy usage for the day. The dial indicates energyavailable in the battery.

FIG. 2 is an example of a screen display for login to a clientapplication consistent with the present disclosure. In this example, thelogin screen is shown for a smart phone type of portable device.Suitable applications or “apps” may be provided for various differentclient devices as noted, and a similar application may be deployed on avehicle head unit. In FIGS. 3-53, a smart phone or iPhone display screenis used by way of illustration and not limitation. Any display,including a windshield “head up” display, may be used.

Referring again to FIG. 1, the server 12 may store an application 20 tobe downloaded to a personal portable device for operation thereon. Inone example, the application 20 is downloaded to a personal portabledevice, such as a mobile phone. The personal portable device operatingthe application can remotely control a component of the vehicle.

In one example, the downloaded application causes the screen shown inFIG. 3 to be displayed on the personal portable device. The “charge nowbutton” causes the personal portable device to transmit a signal thatcauses the electric vehicle to begin charging (so long as the electricvehicle is plugged in to a utility power source). Other components ofthe vehicle may be controlled using the Remote Control feature furtherdescribed below.

FIG. 4 is an example of a client application screen display showingicons corresponding to a variety of available user services andfeatures. Other features may be added or removed. For example, newapplications later developed may be downloaded from the server andinstalled on the client device.

FIG. 5 is an example of a client application screen display showingexamples of remote control features. These may include operation ofvehicle door locks, horn, lights, and motor startup or stop. The remotecontrol may indicate current cabin temperature, and may enable remotecontrol of heating or cooling operations to condition to cabintemperature prior to user boarding.

FIG. 6 is an example of a client application screen display forutilizing a feature that may be called Drive Times. This enables a userto specify regular or repeating “drive times” or trips. For example, acommute between home and work locations may define a drive time. Thetimes, days of the week and locations may be “programmed” and stored. Ifa car is plugged into a charger at work all day, for example, it may tryto take advantage of variations in charging cost (prices) if it needscharging for only, say one hour. FIG. 7 shows an example of a listing ofdrive times by day of the week. It also shows a desired cabintemperature for departure time. The remote control feature may utilizethis information to begin pre-heating the cabin if necessary in advanceof the scheduled departure or “drive time.” A button at the bottom ofthe screen enables adding a new drive time; it may be used to invoke ascreen display like that shown in FIG. 8.

FIG. 8 is an example of a client application screen display for adding anew drive time. A time of day is specified, and days of the week areselected. Optional pre-conditioning of the cabin may be selected, aswell as pre-heating seats. FIG. 9 is a continuation of the screendisplay of FIG. 8, which may be accessed by scrolling. It shows checkboxes for selecting days of the week for the subject drive time. Seediscussion of commutes below with regard to FIG. 38.

FIG. 10 is an example of a client application screen display regarding“Eco-Charge Profiles,” a feature designed to take advantage ofvariations in electricity pricing for charging an electric vehicle. Eachprofile may be associated to a specific location where charging isavailable. FIG. 11 is an example of a client application screen displayshowing a listing of eco-charge profiles per location. A button at thebottom enables adding a new location. FIG. 12 is an example of a clientapplication screen display for selecting a charging location to define acharge profile, and assigning a name to the location.

FIG. 13 shows an example of a client application screen displaycomprising a map showing the user's current location, and a currentlocation of the electric vehicle. A button at the bottom of the screendisplay may be used to request walking directions to the vehicle. FIG.14 is a map display showing a suggested route for walking from theuser's current location to the current location of the electric vehicle.The current location of the vehicle may be obtained in various ways, forexample, by querying the vehicle (from the server or the handheldclient), or accessing a stop location from the last trip historydatabase record, or a temporary data buffer. Further, a stop locationcan also be recorded via the portable device (with GPS) manually by theuser or automatically when the vehicle is Key-Off. A button at the topof the display enables toggling to a list view of the suggested route.FIG. 15 shows the suggested walking route of FIG. 14 in a list view.

Travel Planning for EV

FIG. 16 is an example of a client application screen display for atravel planner feature. The travel planner may be used to calculateroutes based on current location and taking into account the vehiclecharge level. If necessary, a route may be modified in order to visit acharging station along the way. FIG. 17 shows an example of a clientapplication screen display for adding a route point or adding a chargingstation for planning a trip. The display may include indications of thecar's current location, charge level and estimated range. Planning atrip may involve the following display screen interactions. FIG. 18 isan example of a client application screen display for entering a placeor address as part of planning a trip. FIG. 19 shows a listing oflocations that were found based on the data entered in FIG. 18. In FIG.19, the listed locations preferably are color coded, or some otherindicator provided, to indicate whether the vehicle is capable ofreaching the location based on current location and charge level. Forexample, green color may be used to indicate that the vehicle can reachthe corresponding location; yellow may be used to indicate the vehicleprobably can reach the location, but that is not certain; and red may beused to indicate the corresponding location is out of range. A buttonmay be provided to switch to map view.

FIG. 20 is a map display showing the locations that are listed in thescreen display of FIG. 19, enabling user selection of a desired locationor route point by touching the screen at the corresponding locationindicator. Preferably, the locations are color coded on the map asdescribed with regard to FIG. 19. Referring now to FIG. 21, the user hasselected a location (from the list or the map view), and the selectedroute point is now listed, again color coded, with an indication of thedistance to that route point. The process can be repeated to identifyand select additional route points to add to the trip. When ready, theuser can press the “Calculate Route” button at the bottom to obtain arecommended route.

Charging Stations

Referring now to FIG. 22, this screen display enables conducting asearch for charging stations. One may search near a current location ofthe EV, or the user can enter another location, street address or aspecific charge station name. FIG. 23 is a continuation of the screendisplay of FIG. 22 which may be accessed, for example, by scrolling. Thecharge station search function, in a preferred embodiment, may includespecification of a charging station brand, charger levels (types ofchargers) and other criteria such as network stations only, freestations only, public stations, etc. The search is enabled, in someembodiments, by interaction with the server 12 of FIG. 1, acting incommunication with one or more charging stations networks (30 in FIG.1). In some examples, the server 12 provides an aggregator functionacross multiple brands or networks of charging stations. It may selectfavorites, find best pricing, or apply other criteria including but notlimited to those mentioned above.

FIG. 24 is an example of a client application screen display showing alisting of charging stations identified by a search. FIG. 25 is a mapdisplay showing locations of the charging stations that are listed inthe display of FIG. 24. Corresponding distances may be listed for eachstation. Brand names, and/or other indicia may be included as well, forexample, current pricing or special promotions. As before, color codingmay be used. From the list view or the map view, a user may select acharging station to visit. Details of the selected station may then bedisplayed as illustrated in the example of FIG. 26. Details may includecharger levels, current status (availability for charging), location,hours, phone and access details, photos of the location, user reviewsand comments.

FIG. 27 shows a selected charging station added to a trip plan similarto adding a route point. In an embodiment, a user can slide route pointsup or down on the display screen (finger slide gesture) to reorder thetrip, and then it can be recalculated. FIG. 28 is an example of a clientapplication screen display arranged for a user to enter a home address,which may be used as an anchor point or route point. FIG. 29 illustratesadding the user's home location as a route point for a trip plan. Theuser's home may have charging capability. In that case, it may be listedin an eco charge profile as explained above with regard to FIG. 10.

FIG. 30 is an example of a client application screen display regardingplanning a proposed trip. This display may result from a “calculateroute” command. It provides options to switch to map view (FIG. 32). Thedisplay may indicate the vehicle's ability to reach listed destinationsbased on current charge level. It may show the route details, withbuttons to enable editing the route, and/or sending the route to thevehicle. FIG. 31 is a continuation from FIG. 30 showing details of theproposed route. FIG. 32 is an example of a map screen displayillustrating the proposed route, with a button to toggle to list view.As noted earlier, color-coding preferably is included in map viewsand/or list views of locations or route points.

Referring now to FIG. 33, this illustrates a search interface forfinding a charging station independently of travel planning. Thecharging station searching feature was described above with regard toFIGS. 22-23. FIG. 34 is a continuation of the display of FIG. 33 showingmore details for a charging station search. FIG. 35 is an example of ascreen display showing a listing of charging stations that were foundpursuant to the search defined in FIGS. 33-34. FIG. 36 is anillustration of the charging station search results in a map view.

Charging Station Reservations

FIG. 37 is an example of a screen display showing details of a selectedcharging station, as mentioned above, with an option to reserve chargingtime at the charging station. FIG. 47 is an example of a clientapplication screen display for making a reservation at the selectedcharging station identified in FIG. 37. To do so, the user may log intoa pre-established account with a username and password. A date isselected for the charging reservation, along with a charging start timeand duration. FIG. 48 is a continuation of the prior screen display. Theclient application may indicate a price for the charging session. It mayobtain this information from the charging network, or via the centralserver. The client app may provide for a reminder. In a presentlypreferred implementation, the central server implements the chargingreservation feature by interaction with a charging station network, forexample using an API. A “Reserve” button on the app display screen maybe used to make the reservation. FIG. 49 shows an example of a screendisplay confirming a charging station reservation, and showing thereservation details. FIG. 50 is an example of a screen display forcanceling a reservation at an EV charging station. In some cases, apenalty may be charged for canceling a reservation.

Commuting Assistance for EV

FIG. 38 is an example of a client application screen display showing anupcoming commute and a series of stored commutes, along with travel timefor each commute based on traffic conditions. In case of heavy or slowtraffic along the upcoming commute route, the system may recommend analternate route or departure time. Traffic and route information may beprovided via the server.

FIG. 51 is an example of a client application screen display regarding astored commute to work, with information on travel time and an alternateroute. An alternate route may be one created by the system to presentthe driver with a time saving option. Such alternate routes may beevaluated for energy demands and presented only if the EV has sufficientbattery reserves.

FIG. 52 is an example of a map display illustrating an alternate routeresponsive to the button on FIG. 51, with a button to show traffic. FIG.53 is an example of a screen display of the map of FIG. 52 including anindication of traffic conditions, for example, by using color.

FIG. 39 is an example of a client application screen display showing ahealth report for the electric vehicle. FIG. 40 is an example of aclient application screen display showing information about a user'sdriving style, which preferably is based on a history of trips, anddisplaying information reflecting monetary savings and energyconsumption for the subject vehicle. This type of report can begenerated by the server using the history database described above.

FIG. 41 is an example of screen display showing aggregated informationfor a given group, model or fleet of electric vehicles. FIG. 42 is anexample of a client application screen display for managing a user'saccount and other operations.

FIGS. 43-45 enable maintaining a user profile. FIG. 46 is an example ofa screen display for updating a user password for a mobile applicationaccount.

FIG. 54 is an example of a web page interface for electric vehicleservices. The various features illustrated in FIG. 54 were describedabove with regard to a smart phone user interface.

It will be obvious to those having skill in the art that many changesmay be made to the details of the above-described embodiments withoutdeparting from the underlying principles of the invention. The scope ofthe present invention should, therefore, be determined only by thefollowing claims.

The invention claimed is:
 1. A computer-implemented method comprising:storing historical driving data for an electric vehicle (EV) in amemory, the driving data reflecting a plurality of driving trips of theEV; including in the historical driving data, for each driving trip ofthe plurality of driving trips of the EV, at least data indicating adistance traveled, a corresponding change in vehicle charge level, and adate or day of the week: in a processor, analyzing the historicaldriving data to determine a user's driving style; and displaying adriving range estimate on an electronic display screen, wherein thedisplayed driving range estimate is calculated based on the user'sdriving style.
 2. The computer-implemented method of claim 1 and furthercomprising: in the processor, analyzing the historical driving data todetermine a monetary savings; and displaying an indication of themonetary savings on the electronic display screen.
 3. Thecomputer-implemented method of claim 1 and further comprising: includingtemperature data in the historical driving data for the EV; determininga current local temperature; comparing the current local temperature toan average temperature reflected in the historical driving data todetermine an expected energy usage of the EV; and displaying anindication of readiness status for the EV on the electronic displayscreen responsive to the said temperature comparison.
 4. Thecomputer-implemented method of claim 1 and further comprising: analyzingthe historical driving data for the EV to determine a batterycharge-discharge profile for the EV.
 5. The computer-implemented methodof claim 1 and further comprising: providing a server computer;arranging the server computer for communications with the EV to acquirethe historical driving data from the EV and to determine a currentcharge level of the EV; determining the user's driving style in theserver computer; further arranging the server computer forcommunications with a client device, wherein the electronic displayscreen comprises an electronic display screen of the client device; andtransmitting data about the driving range estimate from the servercomputer to the client device for display of the driving range estimateon the electronic display screen of the client device.
 6. Thecomputer-implemented method of claim 5 wherein the client devicecomprises a smart phone or tablet computing device.
 7. Thecomputer-implemented method of claim 5 wherein the client devicecomprises a head unit of the EV.
 8. The computer-implemented method ofclaim 5 and further comprising: including vehicle speed versus time dataand identification of a driver in the acquired historical driving datafor the EV; and analyzing the historical driving data at the servercomputer to determine an acceleration and braking profile for theidentified driver of the EV.
 9. The computer-implemented method of claim1 and further comprising: providing a server computer; providing anapplication program executable on a client device and arranged toacquire the historical driving data from the EV; and transmitting theacquired historical driving data from the client device to the servercomputer for storage in a database of historical driving data for theEV.
 10. The computer-implemented method of claim 9 wherein: theanalyzing the historical driving data to determine the user's drivingstyle is carried out in the server computer, and results of theanalyzing are communicated from the server computer to the clientdevice.
 11. The computer-implemented method of claim 1 and furthercomprising: in the processor, analyzing the historical driving data todetermine energy savings; and displaying an indication of the energysavings on the electronic display screen.
 12. The computer-implementedmethod of claim 1 and further comprising: providing a server computer;arranging the server computer for communications with the EV to acquirethe historical driving data from the EV and to determine a currentcharge level of the EV; determining estimated energy savings in theserver computer based on the historical driving data; further arrangingthe server computer for communications with a client device, wherein theelectronic display screen comprises an electronic display screen of theclient device; and transmitting estimated energy savings from the servercomputer to the client device for display of an indication of theestimated energy savings on the electronic display screen of the clientdevice.
 13. A computer-implemented method comprising: storing historicaldriving data for an electric vehicle (EV) in a memory, the driving datareflecting a plurality of driving trips of the EV; including in thehistorical driving data, for each driving trip of the plurality ofdriving trips of the EV, at least data indicating a distance traveled, acorresponding change in vehicle charge level, and a date or day of theweek: in a processor, analyzing the historical driving data to determinea user's driving style; and displaying a comparison of an energy usageestimate with a current charge level of the EV on an electronic displayscreen, wherein the energy usage estimate corresponds to a given timeperiod and is calculated based on the user's driving style.
 14. Thecomputer-implemented method of claim 13 and further comprising:providing a server computer; arranging the server computer forcommunications with the EV to acquire the historical driving data fromthe EV and to determine a current charge level of the EV; determiningthe user's driving style in the server computer; further arranging theserver computer for communications with a client device, wherein theelectronic display screen comprises an electronic display screen of theclient device; and transmitting data about the energy usage estimatefrom the server computer to the client device for display of the energyusage estimate on the electronic display screen of the client device.15. The computer-implemented method of claim 14, wherein the clientdevice is arranged to remotely control a component of the EV.
 16. Thecomputer-implemented method of claim 14, wherein the client device isarranged to transmit a signal that causes the EV to begin charging solong as the EV is plugged into a utility power source.
 17. Thecomputer-implemented method of claim 16, wherein the client deviceincludes a user interface selectable by a person to cause the clientdevice to transmit the signal.
 18. The computer-implemented method ofclaim 17, wherein the client device displays the comparison co-locatedwith the user interface.
 19. The computer-implemented method of claim 14and further comprising: providing an application program executable onthe client device and arranged to acquire the historical driving datafrom the EV; and transmitting the acquired historical driving data fromthe client device to the server computer for storage in a database ofhistorical driving data for the EV.
 20. The computer-implemented methodof claim 19, wherein the client device comprises: a mobile device incommunication with the EV, or an interface installed in the EV.